
APAR= II09212
CA400OS2OPT DATABASE AND ODBC INFORMATION


** Last updated 7/20/96 **

** Special note **
When a backslash is required for a directory name, it has
been replaced with a "". This is due to the fact that the
backslash does not print correctly. Make sure you replace
all "" symbols with the backslash.


Manual installation instructions for the Client Access/400 for
Windows 3.1 (WIN16) ODBC driver for use in WIN-OS2.
______________________________________________________________

These instructions describe how to make the ODBC driver packaged
with the Client Access/400 for Windows 3.1 (WIN16) client to be
used with the DOS Extended client or most competing clients
(for example, NetSoft). These instructions do not apply to
users of the new Windows 3.1 client. Because this involves a
manual install of the ODBC drvier, no automatic updates are
done if the PCSUPDT function is used. You are responsible for
determining if later versions of the client ODBC code exist
on the server and then installing those later version on the
client.

NOTE:  These steps have not been fully tested and are
       not officially supported.  These steps should be
       followed at your own risk.  Please consult your AS/400
       administrator or IBM Support Line representative if
       you have questions about this document.

Prerequisites for manually installing the V3R1 ODBC driver

REQUIREMENTS FOR ALL USERS

o Product 5763XC1 must be installed on the V3R1 AS/400.

o CUM 5070 (or later) must be applied on the system after
  5763XC1 is installed.

o PTFs SF22711 (5763XC1) and SF22323 (5763SS1) or later must
  be installed.

REQUIREMENTS FOR OS/2 USERS

o If you are using OS/2, it must be at version 2.11 or Warp
  (OS/2 version 3.0) (use the SYSLEVEL command to find out
  what version you are using).

o If you are using Communications Manager/2, it must be at
  version 1.11 or later (SYSLEVEL will show the version of
  this as well).

o DOS Native VDM settings should be set as stated in the Using
  V2R3 DOS and OS/2 PC Support Under OS/2 2.1, GG24-4070.

o Both OS2 and Extended DOS Client Access must be updated and
  current to the R310 system PTF level (Look in the first line
  of C:PCSQPTFIDX and C:PCSOS2QPTFIDX.  The PCS level seems
  to always get overlooked.).

o You must use STARTPCS.BAT for the VDM (the environment
  variables EHNP and EHNL must be set correctly.  See the
  following for details.)

ODBC SETUP FOR ALL NON-CLIENT ACCESS for Windows 3.11 CLIENTS
________________________________________________________________

1. You will need to copy several files to an 'old' shared
   folder so that you can copy the files to the PC. This can
   be done from the AS/400 command line by means of the
   NEW CPY command, not the PC copy command. (NOTE: the x's
   and y's are to be substituted by a directory name of your
   choosing.)  The instructions apply to R311 CA/400.

MD '/qdls/xxxxxxxx'
MD '/qdls/xxxxxxxx/mri2924'
MD '/qdls/yyyyyyyy'
MD '/qdls/yyyyyyyy/system'
CPY OBJ('/qpwxcwn/ehnodbc3.dll') TODIR('/qdls/xxxxxxxx')
CPY OBJ('/qpwxcwn/ehnstp3.dll') TODIR('/qdls/xxxxxxxx')
CPY OBJ('/qpwxcwn/mri2924/ehnodbc3.*')
    TODIR('/qdls/mri2924/xxxxxxxx')
CPY OBJ('/qpwxcwn/ctl3dv2.dll') TODIR('/qdls/yyyyyyyy/system')
CPY OBJ('/qpwxcwn/odbc.dll') TODIR('/qdls/yyyyyyyy/system')
CPY OBJ('/qpwxcwn/odbcadm.exe') TODIR('/qdls/yyyyyyyy')
CPY OBJ('/qpwxcwn/odbcadm.hlp') TODIR('/qdls/yyyyyyyy')
CPY OBJ('/qpwxcwn/odbcinst.dll') TODIR('/qdls/yyyyyyyy')

NOTE: For NetSoft users only, if you are using the NetSoft
      product to access the AS/400, you may need to copy some
      additional files to the PC.  Some of the supplied files
      that come with NetSoft (the EHN*.DLL files) are out of
      date. For example:  "CPY OBJ('/qpwxcwn/ehn*.dll')
      TODIR('/qdls/yyyyyyyy/system')"

2. Copy these files by means of the COPY or XCOPY command
   (using shared folders) to the proper directory:
   C:PCS, C:PCSMRI2924, C:WINDOWS and C:WINDOWSSYSTEM.

NOTES:

a. You may want to make sure you do not currently have any of
   these files in these directories.  If so, you should back
   them up.

b. NetSoft users, make sure you back up your EHN*.DLL files in
   your WINDOWSSYSTEM directory.

          XCOPY I:xxxxxxxx*.* /S C:PCS
          XCOPY I:yyyyyyyy*.* /S C:WINDOWS

c. WINOS2 users, substitute C:OS2MDOSWINOS2 for C:WINDOWS
   for this step and subsequent steps.

3. If you have already installed the old V2R3, V3R0M5, or
   Extended DOS V3R1 ODBC driver or some other ODBC driver, the
   only thing you should have to do is make an extra entry in
   the C:WINDOWSODBCINST.INI file.  The entries you need to
   to add are:

     <Client Access/400 ODBC Driver>
     Driver=C:PCSEHNODBC3.DLL
     Setup=C:PCSEHNSTP3.DLL

     <ODBC Drivers>
     Client Access/400 ODBC Driver=Installed

     (replace the '<' and '>' with square brackets)

4. Edit the C: WINDOWS WIN.INI file and add the following to the
   bottom:

     <CAWIN>
     EHNP=C:PCS
     EHNL=2924

     (replace the '<' and '>' with square brackets)

5. Edit the C:AUTOEXEC.BAT file and add the following lines to
   the top (if using the STARTPCS.BAT, this is done for you):

     SET EHNP=C:PCS
     SET EHNL=2924

6. Start Windows and add a new program item to the Client Access
   program group through the Program Manager's FILE/NEW menu
   option.

7. Choose WINDOWSODBCADM.EXE for the program name and WINDOWS
   for the working directory.  Name the new program item ODBC
   Administration.

8. Use the ODBC administration facility to add a new datasource
   that will use the ODBC driver that you just installed.

You should now have a working version of the V3R1 Client
Access/400 for Windows ODBC driver.


